home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19980901-19981211
/
000092_news@newsmaster….columbia.edu _Thu Oct 1 14:09:44 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id OAA05408
for <kermit.misc@watsun.cc.columbia.edu>; Thu, 1 Oct 1998 14:09:40 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id OAA16787
for kermit.misc@watsun; Thu, 1 Oct 1998 14:09:38 -0400 (EDT)
Path: news.columbia.edu!sol.ctr.columbia.edu!news.mindlink.net!paralynx!paralynx-2!news.mindlink.net!paralynx!paralynx-3!paralynx!paralynx-4!van-bc!paralynx!paralynx-1!cyclone.bc.net!logbridge.uoregon.edu!newsfeed.berkeley.edu!peerfeed.ncal.verio.net!bug.rahul.net!samba.rahul.net!rahul.net!a2i!dold.a2i!dold
From: dold@82.usenet.us.com
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Telnet disconnect
Date: 1 Oct 1998 16:39:49 GMT
Organization: a2i network
Lines: 36
Message-ID: <6v0b8l$ppa$1@samba.rahul.net>
References: <F04wA5.DqL@cix.compulink.co.uk>
Reply-To: dold@network.rahul.net
NNTP-Posting-Host: waltz.rahul.net
NNTP-Posting-User: dold
X-Newsreader: TIN [version 1.2 PL2]
X-Comment: Encoded From: line allows replies that preserve original subject
Xref: news.columbia.edu comp.protocols.kermit.misc:9275
Lygo Systems (lsystemsd@cix.compulink.co.uk) wrote:
: I have a number of users connecting with MS-DOS Kermit telnet sessions
: into Redhat Linux (4.2 & 5.1). If they close the connection with the
: normal Kermit exit command without first logging off, then the telnet
: session is closed on Linux which is just what I want. If, however, they
: reboot their PC with ALT CTL DEL then the session stays active.
This is a historical problem with PC users on the 'net ;-)
If the PC logs off, or shuts down TCP in an orderly fashion, the connection
is terminated, but if the connection just "goes away", the Unix side stays
alive for a length of time indicated in the driver... I believe it is
adjustable as a "KEEPALIVE", but I recall that it wasn't useful for my
application, a few years ago.
The problem seemed to diminish by virtue of Win95, where the TCP driver
stayed "up", instead of earlier systems (like some Mac apps), where the
driver was unloaded abruptly, without a proper disconnect. I don't know
that the Mac case was a reboot, but the problem can be simulated on a PC by
a reboot. I doubt that the typical user reboots when finished with a
telnet session, though, so I suspect it is MS-Kermit being terminated
incorrectly. MSKermit has its own TCP layer, so if it is killed off,
rather than closing the connection, the TCP layer suddenly disappears. The
distant end doesn't find out until the TCP layer is reloaded at some later
time.
If you can implement an idle timeout, that should work to break these
connections. Currently, I implement a separate task, at login time, that
watches the time stamp on the terminal device, and closes the connection if
there is no activity. Unfortunately, a displayed "clock" in elm keeps
updating the screen, and prevents my idle timer from killing a session if
elm is left running.
---
Clarence A Dold - dold@network.rahul.net
- Pope Valley & Napa CA.